Camera as a Vehicle to Identify a Merchant Access Device

ABSTRACT

Systems and methods of conducting a payment transaction using a mobile phone having a camera. The systems and methods receive an image of a merchant access device and optionally location data from a mobile device of a user engaged in the transaction. The systems and methods also receive transaction information associated with the transaction and account information associated with an account of the user. The systems and methods use the information to authorize or decline the transaction.

CROSS-REFERENCES TO RELATED APPLICATIONS

This patent application is a continuation of U.S. application Ser. No.13/051,837, filed Mar. 18, 2011, which claims priority to U.S.Provisional Application No. 61/323,655 filed Apr. 13, 2010, entitled“Camera As A Vehicle To Identify Location,” both of which are herebyincorporated by reference in their entirety for all purposes.

BACKGROUND

Identity theft and identity fraud have become increasingly seriousproblems as devices for engaging in financial transactions haveincreased in number. These fraudulent activities have become very costlyto consumers, merchants, financial institutions, and others.

Prior systems provide various fraud deterrent techniques. For example,near field communications protocols, such as Bluetooth and RFID, allow aconsumer to exchange transaction information with a merchant withoutphysical contact between the consumer's near field communication enabledpayment device and the merchant's near field communication enabledaccess device. The problem is that all consumers do not have paymentdevices that support near field communications. Thus, all consumerscannot take advantage of contactless payment mechanisms.

Embodiments of this disclosure address these and other problems,individually and collectively.

BRIEF SUMMARY

Embodiments of the present invention relate in general to financialtransactions and in particular to systems and methods for using a cameraas a vehicle to identify the location of a merchant access device of amerchant.

According to one embodiment, a method includes acquiring, during atransaction between a consumer and a merchant via a merchant accessdevice associated with the merchant, an image of the merchant accessdevice, the image including characteristics of the merchant accessdevice, and communicating the image to a server computer. The servercomputer subsequently identifies the merchant access device from aplurality of merchant access devices using the characteristics of themerchant access device included in the communicated image.

According to another embodiment, a method includes receiving, during atransaction between a consumer and a merchant via a merchant accessdevice associated with the merchant, an image of the merchant accessdevice, the image including characteristics of the merchant accessdevice, and identifying the merchant access device from a plurality ofmerchant access devices using the characteristics of the merchant accessdevice included in the received image, and sending an authorizationresponse message to the merchant access device. The authorizationresponse message indicates whether or not the transaction is approved.

These and other embodiments of the invention are described in furtherdetailed below.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of an exemplary system for conducting apayment transaction using a camera in a mobile communication device as avehicle to identify a merchant access device, according to oneembodiment of the invention.

FIG. 2A is a diagrammatic representation of a merchant database storingimages of merchant access devices and location data and theirassociation with merchant access device identifiers, according to oneembodiment of the invention.

FIG. 2B is a diagrammatic representation of a consumer database storingphone numbers of mobile communication devices and their association withconsumer account identifiers, according to one embodiment of theinvention.

FIG. 3 is a block diagram of the basic components that may reside in anexemplary mobile communication device in the form of a mobile phone, inaccordance with an embodiment of the disclosure.

FIG. 4 is a block diagram of the basic components that may reside in anexemplary merchant access device, in accordance with an embodiment ofthe disclosure.

FIG. 5 is a flowchart illustrating a method of processing a paymenttransaction using a camera in a mobile communication device as a vehicleto identify a merchant access device.

FIG. 6 is a flowchart illustrating a method for a mobile communicationdevice to facilitate a payment transaction where a camera in the mobilecommunication device is used as a vehicle to identify a merchant accessdevice.

FIG. 7 is a flowchart illustrating a method for a server computer of apayment processing network or a server computer of an issuer tofacilitate a payment transaction where a camera in a mobilecommunication device is used as a vehicle to identify a merchant accessdevice 132.

FIG. 8 is a block diagram of subsystems that may be present in computerapparatuses that are used in a system for conducting a paymenttransaction according to embodiments of the invention.

DETAILED DESCRIPTION

Embodiments of the invention disclosed herein include systems andmethods for using a camera as a vehicle to identify a merchant accessdevice of a merchant.

A consumer may use a mobile communication device such as a cell phone toengage in a transaction with a merchant. The merchant may have amerchant access device such as a Point of Sale terminal to displaytransaction information and, in some cases, receive account informationfrom the consumer. The mobile communication device in embodiments of thepresent invention includes a camera to process transactions with themerchant. The camera enables the consumer to engage in the transactionwith the merchant without providing account information to the merchant.

Instead of providing account information to the merchant, the consumermay use the camera to acquire an image of the merchant access device.Merchant access devices typically have unique characteristics by whichthey can be identified. Accordingly, the image will capture suchcharacteristics. The consumer may then send the image to a server in apayment processing network such as VisaNet via the mobile communicationdevice. The server may then compare the image to images stored in adatabase in order to identify the merchant access device used. In someembodiments, the comparison may be performed by the mobile communicationdevice. The consumer, at the same time, may also provide accountinformation to the server via the mobile communication device. Further,the server may obtain transaction information, such as the amount of thetransaction which needs to be authorized. The server may obtain thetransaction information from either the consumer via the mobilecommunication device or from the merchant.

Once the server has acquired all of this information, the server maythen use such information to determine whether the transaction isauthorized, or send the information to an issuer for authorization. Anauthorization response message may then be returned to the consumer andmerchant via mobile communication device and/or merchant access device.While the account information is used to identify an account associatedwith the consumer, the transaction information is used to identify theamount of the transaction which needs to be authorized, and the image isused to identify the merchant access device so that the authorizationresponse message may be communicated to the appropriate merchant andmerchant access device.

Certain embodiments of the invention may provide one or more advantagesto consumers, merchants, issuers, and others. An advantage to a consumeris that his identification information is more secure. Since theconsumer can communicate the transaction and identification informationdirectly to the payment processing network through his mobilecommunication device, the merchant access device (e.g., point of saleterminal) no longer requires the identification information to conductthe transaction. Thus, the consumer does not need to provide hisidentification information to the merchant access device, whicheliminates the problem of identity theft at the merchant access device.In many cases, identity theft can occur when the merchant access deviceis located at a fraudulent merchant or when the merchant access deviceitself is unauthorized, because it was placed at a legitimate merchantby an unauthorized person. Further, a direct line of communication fromthe consumer to the payment processing network is easier to protect andthus more secure. For example, the mobile communication device caninclude a secure chip with encryption software. Since the servercomputer of the payment processing network communicates directly withthe mobile communication device, the server computer of the paymentprocessing network can provide frequent and timely updates of encryptionsoftware to the mobile communication device. Thus, the consumer'sidentity information is more secure in this system.

Another advantage to a consumer is that the consumer has more controlover his identity information and over the transaction in general. Inprior systems, the consumer had to provide his identity information(e.g., a PAN or personal account number) to the merchant access device(e.g., the point of sale terminal) in order to conduct a transaction. Inthis system, the mobile communication device has much of thefunctionality of a merchant access device. The mobile communicationdevice can be used to initiate, authorize, and/or terminate thetransaction. Since the consumer is in control of the mobilecommunication device, the consumer decides when to conduct thetransaction and to whom he will provide his identity information. Thus,control of the transaction and identity information is given back to theconsumer.

An advantage to merchants and issuers is that these methods and systemsare easier to secure and can prevent monetary losses due to identitytheft. As discussed above, these systems are inherently more secure andthus should reduce fraud and money lost to fraud. Further, the issuercan save money by concentrating their fraud deterrent efforts onprotecting information communicated between the server computer of thepayment processing network and the mobile communication device.

An advantage to the payment processing network is that the network canmore easily secure the communications to the consumer. As discussedabove, the mobile communication device can include a secure chip withencryption software which is frequently updated by the paymentprocessing network. Also, the encryption algorithms can be more complexsince communications are not sent through a series of other entities.

Another advantage to the payment processing network is that the paymentprocessing network can develop a more sophisticated transaction processsince it has a more detailed account of the transaction. The mobilecommunication device can receive greater detail about the transactionand relay it to the payment processing network. With increasedinformation, the payment processing network has the opportunity todevelop new and more sophisticated techniques of processingtransactions.

Certain embodiments of the invention may include none, some, or all ofthe above technical advantages. One or more other technical advantagesmay be readily apparent to one skilled in the art from the figures,descriptions, and claims included herein.

Before discussing specific embodiments of the invention, somedescriptions of some specific terms are provided below.

Transaction information: may be any suitable information related to thetransaction. For example, at least one of a list of the items in thetransaction, a description of the items, item identifiers (e.g., stockkeeping units or SKUs), prices of the items being purchased, the totalnumber of items, the total amount of the transaction, and a transactioncode. A transaction code is associated with a specific transaction andcan be used to identify other transaction information.

Characteristics of the merchant access device: may be unique feature(s)of the merchant access device which may be used to identify the merchantaccess device. For example, a shape of the merchant access device, acolor or arrangement of colors on the merchant access device, anarrangement of elements provided on the merchant access device, wherethe elements includes at least one of a keypad, a display, a magneticstrip card reader, a printer, a smart card reader, an antenna, andinformation indicating a unique identifier associated with the merchantaccess device located outside a display of the merchant access device.

Location data: may be information sufficient to identify a particularlocation. For example, global positioning system (GPS) coordinates,geographical coordinates (i.e., latitude and longitude), UniversalTransverse Mercator (UTM) coordinates, Universal Polar Stereographic(UPS) coordinates, Cartesian coordinates, and a mailing address.

Account information: may be information sufficient to identify aparticular account issued by an issuer. For example, a phone number, analphanumeric sequence (e.g., a name of the consumer, a name of theaccount, etc.), a dialing tone or sequence of dialing tones, an image orsequence of images (e.g., a picture of the consumer, a fingerprint,etc.), and an audio sequence.

Authorization request message: may be a message that includes a consumeraccount identifier. The consumer account identifier may be a paymentcard account identifier associated with a payment card. Theauthorization request message may request that an issuer of the paymentcard authorize a transaction. An authorization request message accordingto an embodiment of the invention may comply with ISO 8583, which is astandard for systems that exchange electronic transactions made bycardholders using payment cards. An authorization request message maycomprise data elements including, in addition to the account identifier,a service code, a card verification value (CVV), and an expiration date.

Authorization response message: may be an issuing financialinstitution's electronic message reply to an authorization request,which may include one or more of the following status indicators:Approval—transaction was approved; Decline—transaction was not approved;or Call Center—response pending more information, merchant must call atoll-free authorization phone number. It may also include anauthorization code, which may be a code that a credit card issuing bankreturns in an electronic message to the merchant's point of sale (POS)terminal that indicates approval of the transaction. The code serves asproof of authorization.

Merchant access device identifier: may be an identifier which identifiesa particular merchant access device. For example, an alphanumericsequence (e.g., a serial number, IP address, MAC address, etc.), apurely alphabetical sequence, a purely numeric sequence, and the like.

Consumer account identifier: may be an identifier which identifies aparticular consumer account. For example, an alphanumeric sequence(e.g., an account number issued by an issuer, a number of a payment cardissued by an issuer, etc.), a purely alphabetical sequence, a purelynumeric sequence, and the like.

I. Exemplary System with Mobile Phone Having Camera

FIG. 1 is a block diagram of an exemplary system 100 for conducting apayment transaction using a camera in a mobile communication device 120as a vehicle to identify a merchant access device 132, according to oneembodiment of the invention. System 100 includes consumer 110, mobilecommunication device 120, merchant 130, acquirer 140, payment processingnetwork 150, and issuer 160.

Consumer 110 may use mobile communication device 120 in a purchasetransaction. Merchant 130 may have merchant access device 132 used toprocess transactions with consumer 110. Consumer 110 may interact withmerchant 130 using mobile communication device 120. Mobile communicationdevice 120 includes a camera and is capable of communicating withpayment processing network 150 and, in some embodiments, issuer 160.Merchant 130 is in communication with acquirer 140. Acquirer 140 is incommunication with issuer 160 through payment processing network 150.Payment processing network 150 is also in communication with merchant130.

Consumer 110 may be an individual or an organization such as a businessthat is capable of using mobile communication device 120 to conduct atransaction such as a purchase of goods and/or services. Consumer 110has an account with issuer 160 that may be associated with mobilecommunication device 120.

Mobile communication device 120 refers to any suitable wireless devicethat allows consumer 110 to conduct transactions with merchant 130 andcommunicate information with other entities such as payment processingnetwork 150 or issuer 160. Some examples of suitable devices includecellular or wireless phones, personal digital assistants (PDAs), pagers,portable computers, and the like. Suitable mobile communication devicescan be hand-held and compact so that they can fit into a consumer'swallet and/or pocket (e.g., pocket-sized). Such mobile communicationdevices may include a cellular antenna, a GPS antenna, a computerreadable medium (CRM) embodied by one or more memory devices, inputelements (e.g., a keypad), output devices (e.g., a screen), amicrophone, a speaker, and a contactless element, all operativelycoupled to a processor. Mobile communication device 120, regardless ofits form, includes a camera (not illustrated) operatively coupled to theprocessor. The camera is operable to acquire images as is known in theart.

Mobile communication device 120 is operable to communicate informationto other system entities in any suitable form. Some examples of suitableforms include a short message service (SMS) message such as a textmessage, a multimedia media message (MMS), a phone call, a voicemessage, a voicemail message, an instant messaging (IM) message, anemail message, etc. Mobile communication device 120 is also operable tocommunicate images acquired via the camera in any suitable form. Someexamples of suitable forms include MMS, IM with imaging capability, anemail message, etc. In some cases, the system entity receiving themessage (e.g., server computer 152 of payment processing network 150)may require a PIN before authorizing the transmission for securitypurposes. Consumer 110 enters the PIN into mobile communicating device120 or other device communicating with the entity. The PIN is then sentto the entity. Once the entity verifies the PIN, the requesting entitywill authorize the transmission of the message. For example, to send anSMS message to server computer 152 of payment processing network 150,server computer 152 of payment processing network 150 may request a PIN,receive the PIN, and verify that the PIN is valid before allowingtransmission of the SMS message.

In embodiments of the invention, issuer 160 may be associated withmobile communication device 120 in any suitable manner. For example,issuer 160 may have an account that is linked to the phone number inmobile communication device 120. In another example, issuer 160 may havea virtual payment card that is stored on mobile communication device120.

Merchant 130 can be any suitable entity or entities that make a paymenttransaction with consumer 110. Merchant 130 may use any suitable methodto make the payment transaction. For example, merchant 130 may be adepartment store, a gas station, a drug store, a grocery store, or othersuitable business.

Merchant access device 132 refers to any suitable device for processingtransactions with merchant 130 and for interacting with mobilecommunication device 120. Suitable access devices may include Point ofSale (POS) devices, cellular phones, PDAs, personal computers (PCs),tablet PCs, handheld specialized readers, set-top boxes, electronic cashregisters (ECRs), automated teller machines (ATMs), virtual cashregisters (VCRs), kiosks, security systems, access systems, and thelike. According to some embodiments, merchant 130 has a plurality ofmerchant access devices. Each merchant access device may then beassociated with a unique identifier that distinguishes it from othermerchant access devices that merchant 130 has. Each merchant accessdevice may also have a unique identifier that distinguishes it frommerchant devices of other merchants. According to other embodiments,merchant 130 only has a single merchant access device.

Merchant access device 132 may use any suitable contact or contactlessmode of operation to communicate data to and from mobile communicationdevice 120. For example, merchant access device 132 can use a wirelesscommunication mode including near field communication such as Bluetooth,infrared, etc. However, benefits from embodiments of the presentinvention are particularly realized when such wireless communicationmodes are not available.

Acquirer 140 can be any suitable entity that has an account for merchant130 and that processes merchant transactions associated with merchantaccess device 132. For example, acquirer 140 may be a bank that operatesa bank account for merchant 130.

Acquirer 140 includes a server computer 142. Server computer 142 refersto a powerful computer or cluster of computers. For example, servercomputer 142 can be a large mainframe, a minicomputer cluster, or agroup of servers functioning as a unit. In one example, server computer142 may be a database server coupled to a Web server (not shown). Servercomputer 142 includes a processor 144 coupled to a CRM 146. CRM 146comprises code for performing the functions of server computer 142,where processor 144 functions to execute the code.

Acquirer 140 may also include a database (not shown) coupled to servercomputer 142. The database refers to any hardware, software, firmware,or combination of the preceding for storing and facilitating retrievalof information. The database may use any of a variety of datastructures, arrangements, and compilations to store and facilitateretrieval of information. The database may store any suitable data.Acquirer 140 may use any suitable wired or wireless network, includingthe Internet, to communicate with other entities.

Payment processing network 150 refers to a network of suitable entitiesthat have information related to the account associated with consumer110 and issued by issuer 160. Payment processing network 150 may alsohave information related to the account associated with merchant 130 andheld by acquirer 140. This information includes profile information andother suitable information that may be used to complete a transactionbetween consumer 110 and merchant 130 involving the account.

Payment processing network 150 may include data processing subsystems,networks, and operations used to support and deliver authorizationservices, exception file services, and clearing and settlement services.An exemplary payment processing network 150 may include VisaNet™.Networks that include VisaNet™ are able to process credit cardtransactions, debit card transactions, and other types of commercialtransactions. VisaNet™, in particular, includes a Visa IntegratedPayments (VIP) system which processes authorization requests and a BaseII system which performs clearing and settlement services.

Payment processing network 150 includes a server computer 152. Servercomputer 152 refers to a powerful computer or cluster of computers. Forexample, server computer 152 can be a large mainframe, a minicomputercluster, or a group of servers functioning as a unit. In one example,server computer 152 may be a database server coupled to a Web server(not shown). Payment processing network 150 may use any suitable wiredor wireless network, including the Internet, to communicate with otherentities.

Server computer 152 includes a CRM 153 and a processor 154 coupled toCRM 153. CRM 153 comprises code for performing the functions of servercomputer 152, where processor 154 functions to execute the code.

Payment processing network 150 may also include a merchant database 156and a consumer database 158 each coupled to server computer 152 suchthat server computer 152 may access information stored in merchantdatabase 156 and consumer database 158. Merchant database 156 andconsumer database 158 refer to any hardware, software, firmware, orcombination of the preceding for storing and facilitating retrieval ofinformation. Merchant database 156 and consumer database 158 may use anyof a variety of data structures, arrangements, and compilations to storeand facilitate retrieval of information. According to some embodiments,merchant database 156 and consumer database 158 are provided as a singledatabase rather than separate databases.

FIG. 2A is a diagrammatic representation of merchant database 156storing images of merchant access devices and location data and theirassociation with merchant access device identifiers, according to oneembodiment of the invention. That is, merchant access device 132 may beassociated with at least one of an image of merchant access device 132and a location data of merchant access device 132. Merchant database 156may store a merchant access device identifier. The merchant accessdevice identifier may be an identifier which identifies a particularmerchant access device. For example, an alphanumeric sequence (e.g., aserial number, IP address, MAC address, etc.), a purely alphabeticalsequence, a purely numeric sequence, and the like. Merchant database 156may also store an association between an identifier of merchant accessdevice 132 and at least one of the image of merchant access device 132and the location data of merchant access device 132. Merchant database156 may also store at least one of the image of merchant access device132 and the location data of merchant access device 132.

According to some embodiments, merchant database 156 may additionally oralternatively store other information indicating characteristics ofmerchant access device 132. For example, merchant database 156 may storeat least one of information indicating a shape of merchant access device132, information indicating a color or arrangement of colors on merchantaccess device 132, information indicating an arrangement of elementsprovided on merchant access device 132, wherein the elements include atleast one of a keypad, a display, a magnetic strip card reader, aprinter, a smart card reader, an antenna, and information indicating aunique identifier associated with the merchant access device locatedoutside a display of the merchant access device. The unique identifiermay be an alphanumeric number or element associated with the merchantaccess device, a serial number associated with the merchant accessdevice, or a barcode associated with the merchant access device. Themerchant access device identifier may be associated with any or all ofthis type of information.

According to some embodiments, merchant database 156 may store varioustypes of location data. For example, merchant database 156 may store atleast one of global positioning system (GPS) coordinates, geographicalcoordinates (i.e., latitude and longitude), Universal TransverseMercator (UTM) coordinates, Universal Polar Stereographic (UPS)coordinates, Cartesian coordinates, a mailing address, and the like.Merchant access device 132 may be associated with any or all of thistype of information.

FIG. 2B is a diagrammatic representation of consumer database 158storing phone numbers of mobile communication devices and theirassociation with consumer account identifiers, according to oneembodiment of the invention. That is, an account for consumer 110 issuedby issuer 160 may be associated with a phone number. Consumer database158 may store a consumer account identifier. The consumer accountidentifier may be an identifier which identifies a particular consumeraccount. For example, an alphanumeric sequence (e.g., an account numberissued by an issuer, a number of a payment card issued by an issuer,etc.), a purely alphabetical sequence, a purely numeric sequence, andthe like. Consumer database 158 may also store the phone number, and anassociation between the consumer account identifier and the phonenumber.

According to some embodiments, consumer database 158 may additionally oralternatively store other account-related information linked to theconsumer account identifier. For example, consumer database 158 maystore an alphanumeric sequence (e.g., a name of the consumer, a name ofthe account, etc.), a dialing tone or sequence of dialing tones, animage or sequence of images (e.g., a picture of the consumer, afingerprint, etc.), an audio sequence, etc. The consumer accountidentifier may be associated with any or all of this type ofinformation.

Returning to FIG. 1, issuer 160 may be any suitable entity that canapprove a transaction, and may optionally open and maintain an accountassociated with consumer 110. For example, issuer 160 may be a bank, abusiness entity such as a retail store, or a governmental entity thatissues a payment account to consumer 110. In many cases, issuer 160 mayalso issue a payment card to consumer 110. In some embodiments, issuer160 may also be the acquirer 140.

Issuer 160 includes a server computer 162. Server computer 162 refers toa powerful computer or cluster of computers. For example, servercomputer 162 can be a large mainframe, a minicomputer cluster, or agroup of servers functioning as a unit. In one example, server computer162 may be a database server coupled to a Web server (not shown). Servercomputer 162 includes a processor 164 coupled to a CRM 166. CRM 166comprises code for performing the functions of server computer 162,where processor 164 functions to execute the code.

Issuer 160 may also include a database (not shown) coupled to servercomputer 162. The database refers to any hardware, software, firmware,or combination of the preceding for storing and facilitating retrievalof information. The database may use any of a variety of datastructures, arrangements, and compilations to store and facilitateretrieval of information. The database may store any suitable data.Issuer 160 may use any suitable wired or wireless network, including theInternet, to communicate with other entities.

In a typical payment transaction between consumer 110 and merchant 130,consumer 110 purchases goods or services at the merchant 130. During thetransaction, merchant access device 132 may show the total purchaseamount and/or may show a listing of the purchased items. At this point,consumer 110 may use a camera in mobile communication device 120 to takea picture of merchant access device 132. Consumer 110 may thencommunicate the picture to server computer 152 of payment processingnetwork 150 or server computer 162 of issuer 160. Most merchant accessdevices are unique in appearance or have unique characteristics, whichcan make them identifiable. This information can be used by a remoterserver computer to determine the exact access device that was used toconduct the transaction. In some embodiments, consumer 110 may also usemobile communication device 120 to send location data to server computer152 of payment processing network 150. The location data may indicate alocation of mobile communication device 120. The location data may beused along with the picture to determine the exact merchant accessdevice that was used to conduct the transaction.

Merchant access devices may have various characteristics which make themunique. For example, unique characteristics for purposes ofidentification may include at least one of a shape of the merchantaccess device, a color or arrangement of colors on the merchant accessdevice, and an arrangement of elements provided on the merchant accessdevice. The elements may be any of those typically found on merchantaccess devices. For example, they may include at least one of a keypad,a display, a magnetic strip card reader, a printer, a smart card reader,and an antenna. Other unique characteristics may include a uniqueidentifier associated with the merchant access device. For example, theunique identifier may be an alphanumeric number or element associatedwith the merchant access device, a serial number associated with themerchant access device, or a barcode associated with the merchant accessdevice. In some embodiments, the unique identifier is provided on adisplay of the merchant access device. In other embodiments, the uniqueidentifier is provided on portions of the merchant access device otherthan the display.

According to some embodiments, identification of a merchant may besufficient to identify a particular merchant access device. For example,where a merchant only has a single merchant access device,identification of the merchant is sufficient to identify the merchantaccess device. In such cases, merchant access devices may need onlyprovide characteristics sufficient to identify the merchant. Forexample, unique characteristics may include at least one of a trademarkassociated with the merchant, a structural element of a merchant accessdevice provided only to a particular merchant; a graphical element of amerchant access device provided only to a particular merchant, analphanumeric number or element associated only with the merchant, and aserial number associated only with the merchant.

According to other embodiments, information indicating uniquecharacteristics of a merchant and/or merchant access device may becombined with location data to identify at least one of a merchantaccess device and a merchant. Various types of location data havepreviously been discussed.

In one embodiment, location data may be generated by mobilecommunication device 120. For example, mobile communication device 120may use a GPS antenna to determine the GPS coordinates of mobilecommunication device. In another embodiment, location data may not begenerated by mobile communication device 120, but instead, may beprovided from another source. For example, if mobile communicationdevice 120 is a mobile telephone, server computer 152 may contact thecarrier hosting mobile communication device 120 in order to receive thelocation data of mobile communication device 120. The location data maybe generated using, for example, triangulation methods. In yet anotherembodiment, location data may be communicated to server computer 152 ofpayment processing network 150 by consumer 110. For example, consumer110 my input location data into mobile communication device 120 whichsubsequently relays such information to server computer 152 of paymentprocessing network 150.

In one embodiment, the image acquired by mobile communication device 120may include the unique characteristics associated with merchant accessdevice 132 along with transaction information. The transactioninformation may include, for example, at least one of a list of theitems in the transaction, a description of the items, item identifiers(e.g., stock keeping units or SKUs), prices of the items beingpurchased, the total number of items, the total amount of thetransaction, and a transaction code. A transaction code is associatedwith a specific transaction and can be used to identify othertransaction information. The transaction information may then be sent toserver computer 152 of payment processing network 150 by mobilecommunication device 120.

In another embodiment, consumer 110 may input transaction informationinto mobile communication device 120. The transaction information maythen be sent to server computer 152 of payment processing network 150 bymobile communication device 120.

In other embodiments, the transaction information may be sent to servercomputer 152 of payment processing network 150 by merchant 130 ormerchant access device 132 instead of mobile communication device 120.For example, the transaction information may be sent directly to servercomputer 152 of payment processing network 150 from merchant accessdevice 132. For another example, the transaction information may be sentto server computer 142 of acquirer 140 from merchant access device 132,and then server computer 142 of acquirer 140 may then subsequently sendthe transaction information to server computer 152 of payment processingnetwork 150. For yet another example, after identifying merchant accessdevice 132, server computer 152 of payment processing network 150 maydirectly communicate with merchant access device 132 in order to obtainthe transaction information.

Using mobile communication device 120, consumer 110 sends accountinformation to server computer 152 of payment processing network 150.The account information identifies an account associated with consumer110 and issued by issuer 160. In one embodiment, consumer 110 may sendthe account information directly to server computer 152 of paymentprocessing network 150. For example, consumer 110 may enter, into mobilecommunication device 120, an account number or other informationrecognized by issuer 160 to identify the account issued to consumer 110.Consumer 110 may then cause mobile communication device 120 to send suchinformation to server computer 152 of payment processing network 150. Inother embodiments, server computer 152 of payment processing network 150may deduce the account associated with consumer using information sentby mobile communication device 120. For example, mobile communicationdevice 120 may send a phone number of mobile communication device 120 toserver computer 152 of payment processing network 150. Server computer152 of payment processing network 150 may then compare the receivedphone number with phone numbers stored in consumer database 158 todetermine a matching phone number. Server computer 152 may then identifya consumer account identifier associated with the matching phone number.As previously described, the consumer account identifier identifies theaccount for consumer 110 issued by issuer 160. In other embodiments,server computer 152 of payment processing network 150 may receive thephone number of mobile communication device 120 from another entity,such as a telecommunications company or network associated with mobilecommunication device 120.

Using the data retrieved from the image and, in some embodiments, thelocation data, server computer 152 of payment processing network 150identifies the particular merchant access device associated withmerchant 130 that is used to perform the payment transaction betweenmerchant 130 and consumer 110. Prior to the transaction, images,geographical locations, or other information about the various merchantaccess devices used at various merchants may be stored in merchantdatabase 156 and may be mapped to merchant access device identifiers.Examples of such information have previously been described, and suchdescriptions are equally applicable herein. Also, a table mappingaccount information such as phone numbers to consumer accountidentifiers may be present in consumer database 158. Examples of suchinformation have also previously been described, and such descriptionsare equally applicable herein. Using information such as this, servercomputer 152 of payment processing network 150 then generates and sendsan authorization request to issuer 160. For example, server computer 152may identify the merchant, the specific merchant access device beingused, and the amount of the transaction, from the information that hasbeen received and from the information in the database. It may alsoidentify the consumer account number (as well as expiration date andother payment card information) from the consumer's phone number. All orsome of this information may be included in the authorization requestmessage that is sent to server computer 162 of issuer 160.

Upon receiving the authorization request, issuer 160 processes theauthorization request message and determines whether to authorize ordecline the transaction. Once issuer 160 decides whether to authorize ordecline the transaction, server computer 162 of issuer 160 generates andsends an authorization response message which indicates whether thetransaction is approved or declined. Issuer 160 may decline thetransaction for a variety of reasons (e.g., insufficient funds, riskytransaction, etc.).

According to one embodiment, issuer 160 sends the authorization responsemessage to server computer 152 of payment processing network 150. Servercomputer 152 then sends the authorization response message to servercomputer 142 of acquirer 140. Server computer 142 of acquirer 140 thenforwards the authorization response message to merchant 130 or merchantaccess device 132. Merchant 130 or merchant access device 132 mayprovide the authorization response message to consumer 110. For example,the data associated with the authorization response message may bedisplayed on a display of merchant access device 132 or may be printedon a receipt. In some cases, server computer 152 of payment processingnetwork 150 sends the authorization response message directly toconsumer 110. For example, the authorization response message may besent from server computer 152 of payment processing network 150 directlyto mobile communication device 120 without being sent through acquirer140 or merchant 130. The data associated with the authorization messagemay then be displayed on a display of mobile communication device 120.

In some cases, payment processing network 150 can authorize thetransaction on behalf of issuer 160. In these cases, payment processingnetwork 150 processes the information received from mobile communicationdevice 120. After processing, server computer 152 of payment processingnetwork 150 has information about the consumer using mobilecommunication device 120, the issuer having an account associated withmobile communication device 120, the merchant and/or merchant accessdevice engaged in the transaction, and the transaction. With thisinformation, server computer 152 of payment processing network 150 candetermine whether to authorize or decline the transaction on behalf ofissuer 160. Server computer 152 sends an authorization response messageto acquirer 140. Server computer 142 of acquirer 140 forwards theauthorization response message to merchant 130 which forwards it toconsumer 110. Server computer 152 may also send a message to issuer 160indicating that the transaction has been authorized on their behalf andincluding other suitable information required by issuer 160 to processthe transaction.

In one embodiment, mobile communication device 120 relays some or allinformation directly to issuer 160. The information may be sent in anysuitable form such as an authorization request message. In thisembodiment, issuer 160 determines whether to authorize or decline thetransaction based on the information received from mobile communicationdevice 120. If issuer 160 requires more information from consumer 110 todecide whether to authorize or decline the transaction, server computer162 of issuer 160 may send a request message for more information toconsumer 110 through mobile communication device 120 (or, in someembodiments, through merchant 130 or merchant access device 132). Onceissuer 160 decides whether to authorize or decline the transaction,server computer 162 of issuer 160 directly or indirectly sends anauthorization response message to at least one of mobile communicationdevice 120, merchant access device 132, and merchant 130.

In another embodiment, server computer 152 of payment processing network150 may send the authorization response message directly to mobilecommunication device 120 operated by consumer 110 instead of to merchantaccess device 132. Consumer 110 can provide the authorization responsemessage to merchant 130 using mobile communication device 120. Forexample, consumer 110 may cause mobile communication device 120 to passby a contactless reader of merchant access device 132 so that themerchant access device 132 can read the authorization response messagefrom mobile communication device 120.

In some embodiments, at least one of merchant database 156 and consumerdatabase 158 are provided in mobile communication device 120. In suchcases, mobile communication device 120 may be operable to perform thecomparisons and identifications using merchant database 156 and consumerdatabase 158 previously described with respect to server computer 152 ofpayment processing network 150. In such cases, after performing suchcomparisons and identifications, mobile communication device 120 maycommunicate the results of such comparisons and identifications to severcomputer 152 of payment processing network 150 or server computer 162 ofissuer 160.

At the end of the day, a normal clearing and settlement process may beconducted. A clearing process is a process of exchanging financialdetails between merchant 130 and issuer 160 to facilitate posting to aconsumer's account and reconciliation of the consumer's settlementposition. Clearing and settlement can occur simultaneously.

Modifications, additions, or omissions may be made to system 100 withoutdeparting from the scope of the disclosure. The components of system 100may be integrated or separated according to particular needs. Forexample, although separate functional blocks are shown for an issuer,payment processing network, and acquirer, some entities perform all ofthese functions and may be included in embodiments of invention.Moreover, the operations of system 100 may be performed by more, fewer,or other system modules. Additionally, operations of system 100 may beperformed using any suitable logic comprising software, hardware, otherlogic, or any suitable combination of the preceding.

II. Exemplary Mobile Communication Device

FIG. 3 is a block diagram of the basic components that may reside in anexemplary mobile communication device 300 in the form of a mobile phone,in accordance with an embodiment of the disclosure. Mobile communicationdevice 300 comprises a CRM 310. CRM 310 may be present within a body312, or may be detachable from it. Body 312 may be in the form a plasticsubstrate, housing, or other structure. CRM 322 may be a memory thatstores data and may be in any suitable form including a magnetic stripe,a memory chip, etc. The memory preferably stores information such asfinancial information, transit information (e.g., as in a subway ortrain pass), access information (e.g., as in access badges), etc.Financial information may include information such as bank accountinformation, bank identification number (BIN), credit or debit cardnumber information, account balance information, expiration date,consumer information such as name, date of birth, etc. Any of thisinformation may be transmitted by mobile communication device 120.

CRM 310, or memory, may further comprise any suitable code. The code maybe suitable to perform any or all of the functionality of mobilecommunication device 300 as described herein. In some embodiments, CRM310, or memory, comprises: a) code for receiving information frommerchant access device 132; b) code for sending information to merchantaccess device 132; c) code for receiving information from merchant 130;d) code for sending information to merchant 130; e) code for sendinginformation to server computer 162 of issuer 160; f) code for sendinginformation to server computer 152 of payment processing network 150; g)code for receiving information from server computer 152 of paymentprocessing network 150; h) code for sending information to servercomputer 162 of issuer 160; and/or i) code for receiving informationfrom server computer 162 of issuer 160.

Mobile communication device 300 also comprises a camera 314. Camera 314is operable to take pictures (i.e., acquire images), and may include anytype of image-acquiring device as is known in the art. Mobilecommunication device 300 may also comprise a GPS antenna 316. GPSantenna 316 is operable to receive transmissions from GPS satellites foridentifying a location of mobile communication device 120. GPS antenna316 may include any type of antenna operable to receive transmissionsfrom GPS satellites as is known in the art.

Mobile communication device 300 may also comprise other elementstypically included in mobile communication devices. For example, mobilecommunication device 300 may also include a processor 318 (e.g., amicroprocessor) for processing the functions of the mobile communicationdevice 300 and an output device 320 (e.g., an electronic display) toallow a consumer to see phone numbers and other information andmessages. Mobile communication device 300 may further include inputelements 322 to allow a consumer to input information into the device, aspeaker 324 to allow the consumer to hear voice communication, music,etc., and a microphone 326 to allow the consumer to transmit her voicethrough mobile communication device 300. Mobile communication device 300may also include a cellular antenna 328 for wireless voice and datatransfer (e.g., voice and data transmission). Although benefits fromembodiments of the present invention are particularly realized when suchwireless communication device 300 does not include a contactlesselement, wireless communication device 300 may still include such anelement. That is, mobile communication device 300 may include acontactless element 330, which is typically implemented in the form of asemiconductor chip (or other data storage element) with an associatedwireless transfer (e.g., data transmission) element, such as an antenna.Contactless element 330 functions to permit the exchange of data and/orcontrol instructions between mobile communication device 300 and anoptional contactless element included in a merchant access device.

Although FIG. 3 shows a number of components, mobile communicationdevice 300 according to embodiments of the invention may comprise anysuitable combination or subset of such components.

III. Exemplary Merchant Access Device

FIG. 4 is a block diagram of the basic components that may reside in anexemplary merchant access device 400, in accordance with an embodimentof the disclosure. Merchant access device 400 may comprise a processor410. It may also comprise a CRM 412, a keypad 414, a magnetic stripreader 416, an output device 418, a network interface 420, and anantenna 422. All of these elements may be operatively coupled toprocessor 410. A housing 424 may house one or more of these components.

CRM 412 may include one or more memory chips, disk drives, etc. CRM 412may store code or instructions for allowing merchant access device 400to operate in the manner described herein. The instructions may beexecuted by processor 410.

CRM 412, or memory, may further comprise any suitable code. The code maybe suitable to cause merchant access device 400 to perform any or all ofthe functionality of merchant access device 400 as described herein. Insome embodiments, CRM 412, or memory, comprises: a) code for receivinginformation from merchant 130; b) code for sending information tomerchant 130; c) code for receiving information from mobilecommunication device 120; d) code for sending information to mobilecommunication device 120; e) code for receiving information fromconsumer 110; f) code for sending information to consumer; g) code forsending information to server computer 142 of acquirer 140; h) code forsending information to server computer 152 of payment processing network150; i) code for sending information to server computer 162 of issuer160; j) code for receiving information from server computer 142 ofacquirer 140; k) code for receiving information from server computer 152of payment processing network 150; and/or I) code for receivinginformation from server computer 162 of issuer 160.

Keypad 414 may be operable to input information such as transactioninformation into merchant access device 400. Magnetic strip reader 416may be operable to read information from a magnetic strip of a card suchas a credit card or a debit card. Output device 418 may include adisplay. The display may display, for example, transaction information.Network interface 420 may be operable to enable merchant access device400 to communicate with other system entities. For example, it mayenable merchant access device 400 to communicate with one or more ofacquirer 140, payment processing network 150, and issuer 160. Antenna422 may be provided to enable merchant access device 400 to operateremotely.

IV. Exemplary Methods of Processing a Payment Transaction Using a MobileCommunication Device Having a Camera

FIG. 5 is a flowchart that illustrates one embodiment of a process ofusing a camera in a mobile communication device as a vehicle to identifya merchant access device.

In step S510, consumer 110 and merchant 130 initiate a transaction usingmerchant access device 132. The transaction may be for the purchase ofgoods or services from merchant 130 by consumer 110. Merchant 130 mayenter transaction information into merchant access device 132, and suchinformation may be stored by merchant access device 132 and displayed toconsumer 110 on a display of merchant access device 132. Various typesof transaction information have previously been described, and suchdescriptions are equally applicable herein.

In step S520, in order to get approval to complete the transaction,consumer 110 acquires an image of merchant access device 132 usingmobile communication device 120. Consumer 110 may have mobilecommunication device 120 in their possession during the transaction.Consumer 110 may use camera 314 of mobile communication device 120 toacquire the image of merchant access device 132.

According to some embodiments, the image includes information sufficientto identify merchant access device 132 from a plurality of merchantaccess devices, such as information indicating characteristics ofmerchant access device 132 as previously described. According to otherembodiments, the image includes information sufficient to identifymerchant 130 from a plurality of merchants, such as informationincluding unique characteristics of merchants as previously described.According to yet other embodiments, the image includes transactioninformation as previously described. For example, the image may includesome or all of transaction information displayed by a display onmerchant access device 132.

In some embodiments, consumer 110 may use camera 314 of mobilecommunication device 120 to acquire an image of the entire merchantaccess device 132 or only portions of merchant access device 132. Theimage may include only portions of merchant access device 132 whichinclude characteristics sufficient to identify at least one of merchant130 and merchant access device 132. The portions may be portions ofmerchant access device 132 excluding output device 320 (e.g., a display)of merchant access device 132.

In step S530, consumer 110 sends the acquired image and, in someembodiments, location data via mobile communication device 120 to servercomputer 152 of payment processing network 150.

Location data indicates a location of mobile communication device 120and may include any of the previously described types of location data.In one embodiment, location data comprises GPS coordinates determined bymobile communication device 120. In another embodiment, mobilecommunication device 120 receives input from consumer 110 indicating alocation of mobile communication device 120. In yet another embodiment,mobile communication device 120 does not send location data; rather, itis sent to server computer 152 of payment processing network 150 byanother source. For example, the carrier hosting mobile communicationdevice 120 may use triangulation methods or the like to determine thelocation of mobile communication device 120 and the carrier may thensend such information to sever computer 152 of payment processingnetwork 150.

In step S540, server computer 152 of payment processing network 150 thenuses the received image and, in some embodiments, the received locationdata to identify merchant access device 132.

In some embodiments, server computer 152 of payment processing network150 uses a received image (or other information indicatingcharacteristics of merchant access devices) to identify merchant accessdevice 132. Prior to the transaction, images (or other informationindicating characteristics of merchant access devices) are stored inmerchant database 156. Examples of such information have previously beendescribed, and such descriptions are equally applicable herein. Theimages are mapped to merchant access device identifiers, where eachmerchant access device identifier identifies a particular merchantaccess device. The merchant access device identifiers and the mappingbetween identifiers and images are also stored in merchant database 156.In response to receiving an image from mobile communication device 120,server computer 152 of payment processing network 150 compares thereceived image with the images stored in merchant database 156 todetermine a matching image. Server computer 152 of payment processingnetwork 150 then locates the merchant access device identifierassociated with the matching image. The merchant access deviceidentifier may then be used to identify the particular merchant accessdevice used in the transaction.

In some embodiments, server computer 152 of payment processing network150 uses both a received image and received location data to identifymerchant access device 132. Prior to the transaction, images andlocation data are stored in merchant database 156. Examples of suchinformation have previously been described, and such descriptions areequally applicable herein. Both the images and location data are mappedto merchant access device identifiers. For example, both a single imageand location data indicating a particular location may be mapped to asingle merchant access device identifier. The merchant access deviceidentifiers and the mapping between identifiers, images, and locationdata are also stored in merchant database 156. In response to receivingan image and location data, server computer 152 of payment processingnetwork 150 compares the received image with the images stored inmerchant database 156 to determine a matching image. Server computer 152may then compare the received location data with the location datastored in merchant database 156 to determine a matching location data.For example, if the location data is a GPS location, the received GPSlocation may be compared with GPS locations stored in merchant database156 to determine a matching GPS location. Server computer 152 of paymentprocessing network 150 then locates the merchant access deviceidentifier associated with the matching image and the matching locationdata.

In some embodiments, server computer 152 of payment processing network150 uses a received image (or other information indicatingcharacteristics of merchant access devices) to identify merchant 130.Prior to the transaction, images (or other information indicatingcharacteristics of merchants) are stored in merchant database 156.Examples of such information have previously been described, and suchdescriptions are equally applicable herein. The images are mapped tomerchant identifiers, where each merchant identifier identifies aparticular merchant. The merchant identifiers and the mapping betweenidentifiers and images are also stored in merchant database 156. Inresponse to receiving an image from mobile communication device 120,server computer 152 of payment processing network 150 compares thereceived image with the images stored in merchant database 156 todetermine a matching image. Server computer 152 of payment processingnetwork 150 then locates the merchant identifier associated with thematching image. The merchant identifier may then be used to identify theparticular merchant used in the transaction. In some embodiments,merchant 130 is only associated with a single merchant access device.Accordingly, by identifying merchant 130, server computer 152 of paymentprocessing network 150 effectively identifiers merchant access device132.

In some embodiments, server computer 152 of payment processing network150 uses both a received image and received location data to identifymerchant 130. Prior to the transaction, images and location data arestored in merchant database 156. Examples of such information havepreviously been described, and such descriptions are equally applicableherein. Both the images and location data are mapped to merchantidentifiers. For example, both a single image and location dataindicating a particular location may be mapped to a single merchantidentifier. The merchant identifiers and the mapping betweenidentifiers, images, and location data are also stored in merchantdatabase 156. In response to receiving an image and location data,server computer 152 of payment processing network 150 compares thereceived image with the images stored in merchant database 156 todetermine a matching image. Server computer 152 may then compare thereceived location data with the location data stored in merchantdatabase 156 to determine a matching location data. For example, if thelocation data is a GPS location, the received GPS location may becompared with GPS locations stored in merchant database 156 to determinea matching GPS location. Server computer 152 of payment processingnetwork 150 then locates the merchant identifier associated with thematching image and the matching location data. The merchant identifiermay then be used to identify the particular merchant used in thetransaction. In some embodiments, merchant 130 is only associated with asingle merchant access device. Accordingly, by identifying merchant 130,server computer 152 of payment processing network 150 effectivelyidentifiers merchant access device 132.

In some embodiments, server computer 152 of payment processing network150 uses a received location data to identify merchant 130 and areceived image to identify merchant access device 132. Prior to thetransaction, images and location data are stored in merchant database156. Examples of such information have previously been described, andsuch descriptions are equally applicable herein. The location data maybe mapped to merchant identifiers, and images may be mapped to merchantaccess device identifiers. According to one embodiment, each merchant isassociated with a set of merchant access devices which the merchant maycontrol. Thus, each merchant identifier may be associated with a set ofmerchant access device identifiers. All of this information may bestored in merchant database 156. In response to receiving an image andlocation data, server computer 152 of payment processing network 150 maycompare the received location data with the location data stored inmerchant database 156 to determine matching location data. Servercomputer 152 may then locate the merchant identifier mapped to thematched location data. Using the merchant identifier, server computer152 may determine the merchant access identifiers associated with themerchant identifier. Server computer 152 may then compare the receiveimage with the images mapped to the associated merchant accessidentifiers. Server computer 152 of payment processing network 150 maythen locate the merchant access device identifier mapped to the matchingimage. In some embodiments, the merchant identifier may be used toidentify the particular merchant used in the transaction. In otherembodiments, the merchant access device identifier may be used toidentify the particular merchant access device used in the transaction.

Techniques for using received image and location data to identifymerchant access devices and merchants are not limited to thosedescribed. Rather, other methods for using at least one of image andlocation data to identify at least one of merchant access devices andmerchants are within the scope of the invention.

In step S550, server computer 152 of payment processing network 150obtains the transaction information. Various types of transactioninformation have previously been described, and such descriptions areequally applicable herein. Further, server computer 152 of paymentprocessing network 150 may obtain the transaction information using oneor more of a variety of techniques.

In one embodiment, mobile communication device 120 communicatestransaction information to server computer 152 of payment processingnetwork 150. The information may be communicated directly to servercomputer 152 of payment processing network 150, or via other entities.Mobile communication device 120 may acquire the transaction informationusing one or more of a variety of techniques. For example, consumer 110may input the transaction information into mobile communication device120. For another example, mobile communication device 120 may take apicture of the transaction information. The transaction information maybe in the same picture as the picture including characteristics of atleast one of a merchant and merchant access device. Alternatively, thetransaction information may be in a different picture. According to someembodiments, the picture including transaction information is sent toserver computer 152 of payment processing network 150. According toother embodiments, mobile communication device 120 extracts thetransaction information from the picture and then sends the transactioninformation to server computer 152 of payment processing network 150.

In another embodiment, the transaction information may be sent to servercomputer 152 of payment processing network 150 by merchant 130 ormerchant access device 132 instead of or in addition to mobilecommunication device 120. For example, the transaction information maybe sent directly to server computer 152 of payment processing network150 from merchant access device 132. For another example, thetransaction information may be sent to server computer 142 of acquirer140 from merchant access device 132, and then server computer 142 ofacquirer 140 may subsequently send the transaction information to servercomputer 152 of payment processing network 150. For yet another example,after identifying merchant access device 132, server computer 152 ofpayment processing network 150 may directly communicate with merchantaccess device 132 in order to get the transaction information needed togenerate the authorization request message.

In step S560, server computer 152 of payment processing network 150receives consumer account information and identifies a consumer accountusing such information.

In some embodiments, server computer 152 of payment processing network150 may deduce an account associated with consumer using a receivedphone number. For example, prior to the transaction, phone numbers maybe stored in consumer database 158. The phone numbers may be mapped toconsumer account identifiers, where each consumer account identifieridentifies an account for consumer 110 issued by issuer 160. Theconsumer account identifiers and the mapping between identifiers andphone numbers are also stored in consumer database 158. In response toreceiving a phone number from mobile communication device 120, servercomputer 152 of payment processing network 150 compares the receivedphone number with the phone numbers stored in consumer database 158 todetermine a matching phone number. Server computer 152 of paymentprocessing network 150 then locates the consumer account identifierassociated with the matching phone number. The consumer accountidentifier may then be used to identify the account for consumer 110issued by issuer 160.

In other embodiments, server computer 152 of payment processing network150 may deduce an account associated with consumer using other receivedaccount-related information. For example, prior to the transaction, usernames may be stored in consumer database 158. The user names may bemapped to consumer account identifiers. Consumer 110 may communicate auser name to server computer 152 of payment processing network 150, forexample, via mobile communication device 120. Server computer 152 ofpayment processing network 150 may then perform matching similar to thatdescribed above with respect to phone numbers so as to identify theaccount for consumer 110 issued by issuer 160. Other account-relatedinformation, as previously described, may similarly be used.

In some embodiments, mobile communication device 120 may directlycommunicate an account identifier to server computer 152 of paymentprocessing network 150. For example, consumer 110 may enter, into mobilecommunication device 120, an account number or other informationrecognized by issuer 160 to identify the account issued to consumer 110.The account number may be entered by at least one of an alphanumericsequence, dialing tone or sequence of dialing tones, image or sequenceof images, audio sequence, etc. Consumer 110 may then cause mobilecommunication device 120 to send such information to server computer 152of payment processing network 150. In such a case, server computer 152may not perform matching as previously described.

In step S570, server computer 152 of payment processing network 150generates and sends an authorization request message to server computer162 of issuer 160 to facilitate completion of the transaction.

In some embodiments, server computer 152 of payment processing network150 uses the merchant access device identifier, transaction information,and consumer account identifier to generate the authorization requestmessage. Server computer 152 may extract, from the transactioninformation, a transaction amount to be authorized. Server computer 152may then generate an authorization request message which requestsauthorization of the transaction amount from the consumer accountidentified by the consumer account identifier. The authorization requestmessage may include merchant access device identifier so that issuer 160may direct a response to the merchant access device identified by themerchant access device identifier.

In other embodiments, server computer 152 of payment processing network150 uses the merchant identifier, transaction information, and consumeraccount identifier to generate the authorization request message so thatissuer 160 may direct a response to the merchant identified by themerchant identifier. In yet other embodiments, server computer 152 ofpayment processing network 150 uses both a merchant identifier and amerchant access device identifier so that issuer 160 may direct aresponse to at least one of the merchant and merchant access device. Inyet other embodiments, server computer 152 of payment processing network150 does not include a merchant access device identifier or a merchantidentifier. For example, issuer 160 may provide the response to servercomputer 152 of payment processing network rather than the merchant ormerchant access device. Server computer 152 may then forward theresponse to the merchant or merchant access device.

In step S580, server computer 162 of issuer 160 communicates anauthorization response message to merchant access device 132. Issuer 160may first receive the authorization request message, process theauthorization request to generate an authorization response message, andthen send the authorization response message. Processing theauthorization request includes determining whether to authorize ordecline the transaction. The authorization response message is a messageindicating whether the transaction is approved or declined. Issuer 160may decline the transaction for a variety of reasons (e.g., insufficientfunds, risky transaction, etc.).

In some embodiments, server computer 162 of issuer 160 identifies themerchant access device using a received merchant access deviceidentifier. Server computer 162 may then send an authorization responsemessage to the identified merchant access device. In other embodimentsserver computer 162 of issuer 160 identifies the merchant using amerchant identifier. Server computer 162 may then send an authorizationresponse message to the identified merchant. In other embodiments servercomputer 162 of issuer 160 sends an authorization response message toserver computer 152 of payment processing network 150. In yet otherembodiments server computer 162 of issuer 160 identifies the mobilecommunication device used in the transaction using, for example, areceived consumer account identifier. Server computer 162 may then sendan authorization response message to consumer 110 or mobilecommunication device 120.

FIG. 6 is a flowchart illustrating a method for mobile communicationdevice 120 to facilitate a payment transaction where camera 314 inmobile communication device 120 is used as a vehicle to identify amerchant access device.

In step S610, mobile communication device 120 acquires an image ofmerchant access device 132. Consumer 110 may have mobile communicationdevice 120 in their possession during the transaction. Consumer 110 mayuse camera 314 on mobile communication device 120 to acquire an image ofportions of or the entire merchant access device 132.

According to some embodiments, the image includes unique characteristicsof merchant access device 132 as previously described. The uniquecharacteristics may be sufficient to identify merchant access device 132from a plurality of merchant access devices. According to otherembodiments, the image includes information sufficient to identifymerchant 130 from a plurality of merchants. For example, the image mayinclude unique characteristics of merchant 130 as previously described.According to yet other embodiments, the image includes transactioninformation as previously described. For example, the image may includesome or all of transaction information displayed by a display onmerchant access device 132.

In some embodiments, consumer 110 may use camera 314 of mobilecommunication device 120 to acquire an image of only portions ofmerchant access device 132. The image may include only portions ofmerchant access device 132 which include characteristics sufficient toidentify at least one of merchant 130 and merchant access device 132.The portions may be portions of merchant access device 132 excluding adisplay of merchant access device 132.

In step S620, mobile communication device 120 obtains location data ofmobile communication device 120.

Various types of location data have been previously described, and suchdescriptions are equally applicable herein. Further, various techniquesfor obtaining such location data have also been previously described,and such descriptions are equally applicable herein. For example,according to one embodiment, mobile communication device 120 identifiesa GPS location of mobile communication device 120. In such a case,mobile communication device 120 may use GPS antenna 316 to receivetransmissions from GPS satellites. Mobile communication device 120 maythen use processor 318 to identify a location of mobile communicationdevice 120 using the received transmissions. For another example, mobilecommunication device 120 may receive location data from consumer 110. Insuch a case, consumer 110 may input location data into the mobilecommunication device 120 via input elements 322.

In step S630, mobile communication device 120 communicates the acquiredimage and location data to server computer 152 of payment processingnetwork 150. For example, mobile communication device 120 maycommunicate the image and location data using cellular antenna 328.

According to some embodiments, mobile communication device 120 maycommunicate some or all of such information in an SMS message such as atext message, an MMS message, a phone call, a voice message, a voicemailmessage, an IM message, an email message, etc.

According to some embodiments, the system entity receiving the message(e.g., payment processing network 150) may require a PIN beforeauthorizing the transmission for security purposes. Consumer 110 entersthe PIN into mobile communicating device 120 or other devicecommunicating with the entity. The PIN is then sent to the entity. Oncethe entity verifies the PIN, the requesting entity will authorize thetransmission of the message. For example, to send an SMS message topayment processing network 150, payment processing network 150 mayrequest a PIN, receive the PIN, and verify that the PIN is valid beforeallowing transmission of the SMS message.

In step S640, mobile communication device 120 communicates transactioninformation to server computer 152 of payment processing network 150.For example, mobile communication device 120 may communicate transactioninformation to server computer 152 of payment processing network 150.The information may be communicated directly to server computer 152 ofpayment processing network 150, or via other entities.

Mobile communication device 120 may first acquire the transactioninformation using one or more of a variety of techniques. Suchtechniques have already been described, and such techniques are equallyapplicable herein. For example, consumer 110 may input the transactioninformation into mobile communication device 120. For another example,mobile communication device 120 may take a picture of the transactioninformation. The transaction information may be in the same picture asthe picture including characteristics of at least one of a merchant andmerchant access device. Alternatively, the transaction information maybe in a different picture. According to some embodiments, the pictureincluding transaction information is sent to server computer 152 ofpayment processing network 150. According to other embodiments, mobilecommunication device 120 extracts the transaction information from thepicture and then sends the transaction information to server computer152 of payment processing network 150.

FIG. 7 is a flowchart illustrating a method for server computer 152 ofpayment processing network 150 or server computer 162 of issuer 160 tofacilitate a payment transaction where a camera in mobile communicationdevice 120 is used as a vehicle to identify merchant access device 132.

In step S710, server computer receives an image from mobilecommunication device 120, location data of mobile communication device120, and consumer account information. The various types of images,location data, and consumer account information have already beendescribed in length, and all such previous descriptions are equallyapplicable herein. Further, various techniques for the server computerto receive such information have also been described in length, and allsuch previous descriptions are equally applicable herein.

In step S720, server computer identifies merchant access device 132 usedfor the transaction. As previously described, server computer mayidentify merchant access device using the received image.

In step S730, server computer obtains transaction information associatedwith the transaction. As previously described, server computer mayobtain transaction information from a variety of entities. For example,server computer may obtain transaction information from mobilecommunication device 120. Alternatively, server computer may obtaintransaction information from merchant 130 or merchant access device 132.

In step S740, server computer identifies a consumer account associatedwith the transaction. As previously described, server computer mayidentify a consumer account associated with the transaction using thereceived phone number of mobile communication device.

In step S750, server computer sends an authorization response message tomerchant access device 132. As previously described, if the servercomputer is server computer 162 of issuer 160, server computer 162 maydirectly send the authorization response message to merchant accessdevice 132 or may send the authorization response message to merchantaccess device 132 via payment processing network 150. Alternatively, ifthe server computer is server computer 152 of payment processing network150, server computer 152 may send the authorization response message tomerchant access device 132.

V. Computer Apparatuses

The various participants and elements of the system shown in FIG. 1 mayoperate one or more computer apparatuses to facilitate the functionsdescribed herein. Any of the elements in FIG. 1 may use any suitablenumber of subsystems to facilitate the functions described herein.Examples of such subsystems or components are shown in FIG. 8. Thesubsystems shown in FIG. 8 are interconnected via a system bus 810.Additional subsystems such as a printer 812, keyboard 814, fixed disk816 (or other memory comprising CRM), monitor 818, which is coupled todisplay adapter 820, and others are shown. Peripherals and input/output(I/O) devices, which couple to I/O controller 822, can be connected tothe computer system by any number of means known in the art, such asserial port 824. For example, serial port 824 or external interface 826can be used to connect the computer apparatus to a wide area networksuch as the Internet, a mouse input device, or a scanner. Theinterconnection via system bus 810 allows central processor 828 tocommunicate with each subsystem and to control the execution ofinstructions from system memory 830 or fixed disk 816, as well as theexchange of information between subsystems. System memory 830 and/orfixed disk 816 may embody a CRM.

The software components or functions described in this application maybe implemented as software code to be executed by one or more processorsusing any suitable computer language such as, for example, Java, C++ orPerl using, for example, conventional or object-oriented techniques. Thesoftware code may be stored as a series of instructions, or commands ona computer-readable medium, such as a random access memory (RAM), aread-only memory (ROM), a magnetic medium such as a hard-drive or afloppy disk, or an optical medium such as a CD-ROM. Any suchcomputer-readable medium may also reside on or within a singlecomputational apparatus, and may be present on or within differentcomputational apparatuses within a system or network.

The present invention can be implemented in the form of control logic insoftware or hardware or a combination of both. The control logic may bestored in an information storage medium as a plurality of instructionsadapted to direct an information processing device to perform a set ofsteps disclosed in embodiments of the present invention. Based on thedisclosure and teachings provided herein, a person of ordinary skill inthe art will appreciate other ways and/or methods to implement thepresent invention.

In embodiments, any of the entities described herein may be embodied bya computer that performs any or all of the functions and stepsdisclosed.

Any recitation of “a”, “an” or “the” is intended to mean “one or more”unless specifically indicated to the contrary.

The above description is illustrative and is not restrictive. Manyvariations of the invention will become apparent to those skilled in theart upon review of the disclosure. The scope of the invention should,therefore, be determined not with reference to the above description,but instead should be determined with reference to the pending claimsalong with their full scope or equivalents.

What is claimed is:
 1. A server computer comprising a processor, acomputer readable storage medium, and software stored on the computerreadable storage medium, the software, when executed by the processor,causing the server computer to perform operations including: receiving,during a transaction between a consumer and a merchant performed via amerchant access device associated with the merchant, from a mobilecommunication device associated with the consumer and used by theconsumer to facilitate the transaction between the consumer and themerchant, an image of the merchant access device, the image includingcharacteristics of the merchant access device located outside of anelectronic display of the merchant access device, the merchant accessdevice being one of a plurality of different merchant access devicesassociated with the merchant; identifying the merchant access devicefrom the plurality of merchant access devices associated with themerchant based on the characteristics of the merchant access devicelocated outside of the electronic display of the merchant access deviceincluded in the received image; and causing an authorization responsemessage to be sent to at least one the merchant access device of theplurality of merchant access devices associated with the merchant, andthe mobile communication device associated with the consumer and used bythe consumer to facilitate the transaction between the consumer and themerchant, wherein the authorization response message indicates whetheror not the transaction is approved.
 2. The server computer of claim 1,wherein characteristics of the merchant access device located outside ofthe electronic display of the merchant access device includes at leastone of: a shape of the merchant access device; a color or arrangement ofcolors on the merchant access device; and an arrangement of elementsprovided on the merchant access device, wherein the elements include atleast one of a keypad, a display, a magnetic strip card reader, aprinter, a smart card reader, and an antenna.
 3. The server computer ofclaim 1, wherein characteristics of the merchant access device locatedoutside of the electronic display of the merchant access device includesa unique identifier associated with the merchant access device locatedoutside of the electronic display of the merchant access device.
 4. Theserver computer of claim 1, wherein the software, when executed by theprocessor, causes the server computer to perform additional operationsincluding: receiving, during the transaction between the consumer andthe merchant, transaction information from at least one of the merchantaccess device and the mobile communication device; and receiving accountinformation indicating an account associated with the consumer.
 5. Theserver computer of claim 4, wherein the transaction information isreceived from the merchant access device.
 6. The server computer ofclaim 4, wherein the transaction information is received from the mobilecommunication device.
 7. The server computer of claim 6, wherein thetransaction information is embedded in the image of the merchant accessdevice received from the mobile communication device, and the software,when executed by the processor, causes the server computer to read thetransaction information from the image.
 8. The server computer of claim6, wherein the transaction information is received separate from theimage of the merchant access device.
 9. The server computer of claim 1,wherein the software, when executed by the processor, causes the servercomputer to perform additional operations including: receiving, duringthe transaction between the consumer and the merchant, locationinformation indicating a location of the mobile communication deviceassociated with the consumer and used by the consumer to facilitate thetransaction between the consumer and the merchant, wherein the merchantaccess device is identified from the plurality of merchant accessdevices associated with the merchant further based on the location ofthe mobile communication device indicated in the received locationinformation.
 10. The server computer of claim 1, further comprising adatabase storing images associated merchant access device identifiers,wherein identifying the merchant access device from the plurality ofmerchant access devices associated with the merchant includes comparingthe received image with the images stored in the database to determine amatching image and the merchant access device identifier associated withthe matching image.
 11. A method for facilitating a transaction betweena consumer and a merchant, comprising: receiving, during a transactionbetween a consumer and a merchant performed via a merchant access deviceassociated with the merchant: an image of the merchant access device,the image including characteristics of the merchant access devicelocated outside of an electronic display of the merchant access device,the merchant access device being one of a plurality of differentmerchant access devices associated with the merchant; and locationinformation indicating a location of a mobile communication deviceassociated with the consumer and used by the consumer to facilitate thetransaction between the consumer and the merchant; identifying themerchant access device from the plurality of merchant access devicesassociated with the merchant based on at least one of: thecharacteristics of the merchant access device located outside of theelectronic display of the merchant access device included in thereceived image, and the location of the mobile communication deviceindicated in the received location information; and causing anauthorization response message to be sent to at least one of themerchant, the merchant access device of the plurality of merchant accessdevices associated with the merchant, and the mobile communicationdevice associated with the consumer, wherein the authorization responsemessage indicates whether or not the transaction is approved.
 12. Themethod of claim 11, wherein identifying the merchant access device fromthe plurality of merchant access devices includes: comparing thereceived image with images stored in a database to determine a matchingimage; comparing the received location information with locations storedin a database to determine a matching location; and locating a merchantaccess device identifier associated with at least one of the matchingimage and the matching location, the merchant access device identifieridentifying the merchant access device from the plurality of merchantaccess devices associated with the merchant.
 13. The method of claim 11,further comprising: identifying the merchant by performing stepsincluding: comparing the received location information with locationsstored in a database to determine a matching location; and locating amerchant identifier associated with the matching location; wherein themerchant access device is identified by performing steps including:comparing the received image with images stored in a database todetermine a matching image; and locating a merchant access deviceidentifier associated with the matching image.
 14. The method of claim11, further comprising: receiving, during the transaction between theconsumer and the merchant, transaction information from at least one ofthe merchant access device and the mobile communication device; andreceiving account information indicating an account associated with theconsumer.
 15. The method of claim 14, wherein the account informationincludes at least one of an account number issued by an issuer, a numberof a payment card issued by an issuer, an purely alphabetic sequence, apurely numeric sequence, an alphanumeric sequence, a name of theconsumer, a name of an account, a dialing tone, a sequence of dialingtones, an image of the consumer, a fingerprint, an audio sequence, and aphone number.
 16. The method of claim 14, further comprising: comparingthe received account information with account information stored in adatabase to determine matching account information, the database havingaccount information associated with consumer account identifiers, theconsumer account identifiers identifying accounts issued by one or moreissuers to consumer; and locating a consumer account identifierassociated with the matching account information; wherein theauthorization response message is caused to be sent based on thereceived transaction information and the consumer account identifier.17. The method of claim 14, wherein the transaction information includesat least one of a list of the items in the transaction, a description ofthe items, item identifiers, prices of the items being purchased, thetotal number of items, the total amount of the transaction, and atransaction code that uniquely identifies the transaction.
 18. Themethod of claim 14, wherein causing an authorization response message tobe sent to includes: generating an authorization request message basedon the received transaction information and account information, theauthorization request message requesting a third party entity to approvethe transaction; and communicating the authorization request message toa computer server associated with the third party entity.
 19. The methodof claim 18, wherein causing an authorization response message to besent further includes: receiving, from the third party entity and inresponse to communicating the authorization request message, anauthorization response message, the authorization response messageindicating whether or not the transaction is approved; and forwardingthe authorization response message to at least one of the merchant, themerchant access device of the plurality of merchant access devicesassociated with the merchant, and the mobile communication deviceassociated with the consumer.
 20. The method of claim 14, whereincausing an authorization response message to be sent includes:determining whether to approve the transaction, generating anauthorization response message; and sending the authorization responsemessage to at least one of the merchant, the merchant access device ofthe plurality of merchant access devices associated with the merchant,and the mobile communication device associated with the consumer.
 21. Atangible non-transitory computer readable storage medium havinginstructions stored thereon that, when executed by a processor, cause atleast one computer to perform operations including: receiving, during atransaction between a consumer and a merchant performed via a merchantaccess device associated with the merchant, location informationindicating a location of a mobile communication device associated withthe consumer and used by the consumer to facilitate the transactionbetween the consumer and the merchant; identifying the merchant accessdevice from the plurality of merchant access devices associated with themerchant based on the location of the mobile communication deviceindicated in the received location information; and causing anauthorization response message to be sent to at least one of themerchant, the merchant access device of the plurality of merchant accessdevices associated with the merchant, and the mobile communicationdevice associated with the consumer, wherein the authorization responsemessage indicates whether or not the transaction is approved.
 22. Thecomputer readable storage medium of claim 21, wherein the locationinformation includes at least one of global positioning systemcoordinates of the mobile communication device, a triangulated positionof the mobile communication device, and a location input by the consumerinto the mobile communication device.
 23. The computer readable storagemedium of claim 21, wherein the instructions, when executed by theprocessor, cause the at least one computer to perform additionaloperations including: receiving, during the transaction between theconsumer and the merchant, transaction information from at least one ofthe merchant access device and the mobile communication device; andreceiving account information indicating an account associated with theconsumer.
 24. The computer readable storage medium of claim 23, whereincausing an authorization response message to be sent includes:generating an authorization request message based on the receivedtransaction information and account information, the authorizationrequest message requesting a third party entity to approve thetransaction; and communicating the authorization request message to acomputer server associated with the third party entity.
 25. The computerreadable storage medium of claim 24, wherein the authorization requestmessage includes an account identifier and an amount of the transaction,and the authorization request message requests authorization of thetransaction amount from a consumer account identified by the consumeraccount identifier.
 26. The computer readable storage medium of claim25, wherein the authorization request further includes at least one ofan identification of the merchant and an identification of the merchantaccess device.
 27. The computer readable storage medium of claim 21,wherein the instructions, when executed by the processor, cause the atleast one computer to perform additional operations including:identifying the merchant based on the location of the mobilecommunication device indicated in the received location information. 28.The computer readable storage medium of claim 21, wherein theinstructions, when executed by the processor, cause the at least onecomputer to perform additional operations including: identifying themerchant based on: the location of the mobile communication deviceindicated in the received location information, and an image of themerchant access device received during the transaction between theconsumer and the merchant.
 29. The computer readable storage medium ofclaim 21, wherein identifying the merchant access device from theplurality of merchant access devices associated with the merchantincludes: comparing the received location information with locationsstored in a database to determine a matching location; and locating amerchant identifier associated with the matching location.
 30. Thecomputer readable storage medium of claim 21, wherein the instructions,when executed by the processor, cause the at least one computer toperform additional operations including: receiving, during thetransaction between the consumer and the merchant, an image of themerchant access device; wherein identifying the merchant access devicefrom the plurality of merchant access devices associated with themerchant includes: comparing the received location information withlocations stored in a database to determine a matching location;comparing the received image with images stored in a database todetermine a matching image; and locating a merchant identifierassociated with both the matching location and the matching image.